Repository navigation
chore: release v0.9.21 - #7385
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
![heygengenesis[bot]](https://avatars.githubusercontent.com/in/2913576?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Approve at 0271d8ce. No blockers.
- Release-only diff: 21 manifests go from
0.9.20to0.9.21(16 packages, 5 plugin/extension files). No0.9.20is left at the head. It also addsreleases/v0.9.21.mdand adocs/changelog.mdxentry, and the two have the same content. - The base is current
main(841e90ffe). The notes list all 19 commits inv0.9.20..main: 3 features, 13 fixes, 1 perf, 2 internal. Every SHA and PR link matches its commit. None is missing and none is listed twice. - This isn't a fix PR, so it doesn't need a
fails without the fix:line. - CI at this head: CI, Docs, CodeQL, Lambda arm64 image, regression, preview-regression, Windows render verification, Player perf, Player Safari perf and PR captures all passed. Comments was skipped.
Nit (not blocking): the drafter keeps commit-subject casing, so the notes say "Hlg … sei … hlg's". "HLG … SEI … HLG's" would read better if you touch the notes again.
miguel-heygen
had a problem deploying
to
npm-publish
November 7, 2026 23:13 — with 
GitHub Actions
Failure
GitHub Actions
Failure
This branch had an error being deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Release v0.9.21: version bump,
releases/v0.9.21.md, and the docs changelog. Merging publishes to npm.Why
Ships cloud uploads that send a big file in parts, so a cut connection resends one part (#7375), a re-encode that limits a large file to fit the cloud's size limit (#7376), and media given as a full path, Windows paths included, going into cloud exports (#7381). It also keeps HDR clips at the same brightness (#7349), plans a long film's chunks once instead of twice (#7382), limits checks to the compositions a project uses (#7369), and puts Safari's picture back on the cut (#7383). It carries the other changes on
mainsince v0.9.20.No visible change
Version bump and changelog only. Each change was captured in its own PR.
Test plan
bun run release:prepare 0.9.21 --no-tagran on currentmain(a fresh clone on a Linux box): it wrote the version bump. It did not write the notes, sobun run changelog:draft 0.9.21 --writewrote them and the summary sentence is by hand.main, signed (the Linux box cannot sign, so the commit was made from the same patch on a signing machine). No tag was created or pushed.oxfmt --checkonreleases/v0.9.21.mdanddocs/changelog.mdx.